option to just skip/autoresolve everything#7974
Merged
NoahTheDuke merged 16 commits intomtgred:masterfrom Mar 4, 2025
Merged
Conversation
Collaborator
Author
|
ok right now this allows you to:
(def automatic-priority
{:pre-bypass 1
:corp-damage 1
:force-discard 1
:lose-clicks 1
:gain-clicks 2
:drain-credits 4
:bypass 4
:lose-credits 4
:pre-gain-credits 5 ;; bladderwort, etc
:gain-credits 6
:pre-draw-cards 7
:draw-cards 8
:post-draw-cards 9
:pre-breach 9
true 10
:trace 11
:corp-lose-tag 11
:last 999 ;; pretty mary wants to trigger last always
})Note that I only tagged the on-encounter, turn begins, and turn ends events for that: those are the ones where I feel like (99% of the time) there aren't any real decisions to make |
Collaborator
Author
|
If there are cards that are part of the prompt, you can click on those cards to click that button. |
NBKelly
commented
Feb 28, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We can mark events as
:skippableor:automatic.If something is skippable, it can be declined without causing any side-effects (most, but not all, optional prompts).
If something is automatic, it can be resolved in an arbitrary order without risking breaking the game (Honestly, this might just be everything - but I'm not entirely sure, so I'm being careful).
When resolving a queued-event (ie encounter, turn begins, turn ends, etc):
Additionally, I made it so that you can:
Closes #4990
And also:
Closes #7984